Using Log Files Catapult Server can log to plain text files (ASCII files), or to a table in an ODBC-compliant database (such as Microsoft SQL Server or Microsoft Access). Separate logs are maintained for the Proxy and RWS services. You administer logging properties using the Logging property sheet of Internet Service Manager.
To determine the path and filename of a text file log, look in the Logging property sheet for the appropriate service. The default is to place Proxy service text file logs at C:\Winnt\System32\Proxylogs\Filename.log, and RWS service text file logs at C:\Winnt\System32\RWSlogs\Filename.log.
The file name takes the format Inyymmdd.log, where:
Catapult Server information is also logged to the Windows NT Application and System logs, which can be viewed using the Windows NT Event View application.
For more information about the Proxy and RWS service logs, see Chapter 5, "Server Configuration.” For more information about Event Viewer and the Application and System logs, see your documentation for Windows NT.
Using Performance Monitor Counters Windows NT includes a tool called Performance Monitor, for tracking computer performance. When you monitor a system, you actually monitor the behavior of its parts. A set of counters exists for the processor, memory, cache, hard disk, processes, and other parts that produce statistical information. Certain counters are standard; others are configured or added with the installation of that software. When Catapult Server is installed on a server, Catapult Server counters are installed into Performance Monitor.
You do not need special privileges to open Performance Monitor. However, you do need to be logged on as a member of the Administrators group to use the diskperf command.
Note that activating counters can increase disk access time.
To start Performance Monitor
To view counters
The Add to Chart dialog box appears.
The counters for that object appear in the Counter list.
The Performance Monitor window returns. Information from the selected counters is displayed.
For more information about using Performance Monitor, see its online Help. Also see your documentation for Windows NT.
The diskperf command turns the counters for disk activity on and off. Diskperf works for a local or a remote computer. After restarting the computer, you can use Performance Monitor to view disk performance data.
To activate the physical and logical disk counters
When Catapult Server is installed, the RWS Server, RWS Server, and RWS Server objects are installed into Performance Monitor. These Performance Monitor objects contain the Catapult Server counters that can be monitored. Statistics from each Catapult Server counter can be displayed in the Performance Monitor window.
The counters in the Internet Access Cache object provide statistics about the Proxy service cache. The following list describes those counters.
The rate at which bytes of data are committed to the URL cache.
The current total number of bytes in the URL cache.
The rate at which bytes of data are retrieved from the URL cache.
The maximum number of bytes that was stored in the URL cache.
The maximum number of URLs that were stored in the URL cache.
The accumulative total number of bytes that have been placed in the URL cache.
The accumulative total number of bytes that have been retrieved from the URL cache.
The accumulative total number of URLS that have been placed in the URL cache.
The accumulative total number of URLs that have been retrieved from the URL cache.
The rate at which URLs are committed to the URL cache.
The rate at which URLs are retrieved from the URL cache.
The current number of URLs in the URL cache.
The counters in the Internet Access Server object provide statistics about the Proxy service. The following list describes those counters.
The rate that data bytes are received by the Proxy service from the clients.
The rate that data bytes are sent by the Proxy service to the clients.
The sum of Client Bytes Received/sec and Client Bytes Sent/sec.
The number of users currently connected to the Proxy service.
The total number of current Domain Name Service (DNS) cache entries.
The total number of DNS cache flushes performed by the Proxy service.
The total number of times the DNS name was found in the cache.
The ratio of cache hits to the total number of cache retrievals. (The ratio of Dns Cache Hits to Dns Cache Retrieval.)
The total number of DNS cache retrievals performed by the Proxy service.
The number of FTP requests that have been made to the Proxy service.
The number of gopher requests that have been made to the Proxy service.
The number of HTTP requests that have been made to the Proxy service.
The rate at which data bytes are received by the Proxy service from Internet servers.
The rate at which data bytes are sent by the Proxy service to Internet servers.
The sum of Inet Bytes Received/sec and Inet Bytes Sent/sec. The total rate of bytes transferred between the Proxy service and Internet servers.
The maximum number of users that have been simultaneously connected to the Proxy service.
The total number of Internet requests that have been denied access to Internet sites by the Proxy service.
The total number of Internet requests that have been granted access to Internet sites by the Proxy service.
The total number of cache fetches for Internet requests that have been performed by the Proxy service.
The total number of unsuccessful Internet requests processed by the Proxy service (due to network or Internet server errors).
The total number of Internet fetches for Internet requests that have been performed by the Proxy service.
The total number of Internet requests received by the Proxy service.
The total number of Internet requests successfully processed by the Proxy service.
The total number of users that have connected to the Proxy service.
The counters in the RWS Server object provide statistics about the RWS service. The following list describes those counters.
Number of connection objects that wait for TCP connection from the client (after a successful remote connect)
Number of active sessions.
Number of active TCP connections. (Active means doing data-pump.)
Note that connections that are in the “connect” call are counted elsewhere.
Total number of active UDP connections.
The number of control channel worker threads that are available (waiting in completion port queue).
The number of data-pump worker threads that are available (waiting in completion port queue).
Total number of connections that are waiting for an inbound “connect ()” call to finish. These are connections from the RWS service to a client, after the RWS service accepted a connection from the Internet on a listening socket.
Number of bytes read by data-pump per second.
Number of bytes written by data-pump per second.
Total number of connections that are waiting for a remote “connect()” call to finish.
The number of control channel worker threads that are alive.
The number of data-pump worker threads that are alive.
Number of calls to gethostname/gethostbyaddr that have failed.
Number of connection objects that wait for TCP connections from the Internet, after a remote listen.
Number of calls to gethostname/gethostbyaddr that have not yet returned
Number of calls to gethostname/gethostbyaddr that have returned successfully.
Using SNMP MIBs
If you monitor your network using Simple Network Management Protocol (SNMP) software, you can use the SNMP Management Information Base (MIB) file provided with Catapult Server. The MIB file can be used by third-party SNMP monitors to enable SNMP monitoring of the Catapult Server Proxy service.
The Catapult Server MIB file is Proxy.mib.
To use the Proxy.mib file with the Windows NT SNMP service, you must first compile it using the MIB compiler that comes with your SNMP software. You must also start the Proxy service before configuring and starting the SNMP service on your Catapult Server computer. Once the SNMP service has been started on both the remote and local computers, you can use SNMP tools to monitor the service.
Note Using SNMP on a gateway that is not secure can expose network routing information to unauthorized users.
© 1996 by Microsoft Corporation. All rights reserved.